The ASP.NET MVC Framework is a web application framework that implements the model-view-controller (MVC) pattern. Based on ASP.NET, it allows software developers to build a Web application as a composition of three roles: Model, View and Controller. A model represents the state of a particular aspect of the application. Frequently, a model maps to a database table with the entries in the table representing the state of the application. A controller handles interactions and updates the model to reflect a change in state of the application, and then passes information to the view. A view accepts necessary information from the controller and renders a user interface to display that.[1]
In April 2009, the ASP.NET MVC source code was released under the Microsoft Public License (MS-PL).[2]
ASP.NET MVC framework is a lightweight, highly testable presentation framework that is integrated with existing ASP.NET features. Some of these integrated features are master pages and membership-based authentication. The MVC framework is defined in the System.Web.Mvc assembly.[3]
The ASP.NET MVC Framework couples the models, views, and controllers using interface-based contracts, thereby allowing each component to be easily tested independently.
Contents |
Date | Version |
---|---|
10 December 2007 | ASP.NET MVC CTP |
13 March 2009 | ASP.NET MVC 1.0[4] |
10 March 2010 | ASP.NET MVC 2.0[5] |
13 January 2011 | ASP.NET MVC 3.0[6] |
20 September 2011 | ASP.NET MVC 4.0 Developer Preview[7] |
The view engines used in the ASP.NET MVC 3 Framework are the Razor View Engine and the Web Forms view engine. Both view engines are part of the MVC 3 framework. By default, the view engine in the MVC framework uses Razor .cshtml
and .vbhtml
, Web Forms .aspx
pages to design the layout of the user interface pages onto which the data is composed. However, different view engines can be used.[8] Additionally, rather than the default ASP.NET Web Forms postback model, any interactions are routed to the controllers using the ASP.NET Routing mechanism. Views can be mapped to REST-friendly URLs.[1]
Other view engines:
|
|